Dynamic allocation of bandwidth in 5g wireless network

ABSTRACT

Spectrum and radio resources associated with a 5G radio unit (RU) of a host network are dynamically allocated amongst one or more guest networks. A provisioning plane receives inputs from a guest network operator that identifies desired times, locations and/or frequency bands for desired network coverage. The provisioning plane responsively identifies bandwidth allocations that meet the requested parameters for exclusive use by the guest network. User equipment (UE) associated with each guest network maintains time and frequency synchronization with the host network, but otherwise limits its communications to the frequency bands allocated to the guest network. By dynamically obtaining physical radio and spectrum resources from a host provider and by scaling backend network capabilities using cloud resources, guest networks for any number of different purposes can be quickly deployed or modified as desired.

TECHNICAL FIELD

The following generally relates to wireless data networks, such as 5Gwireless networks. More particularly, the following relates to systems,devices and automated processes to adaptively share bandwidth within a5G or similar wireless network amongst multiple guest networks.

BACKGROUND

Wireless networks that transport digital data and telephone calls arebecoming increasingly sophisticated. Currently, fifth generation (“5G”)broadband cellular networks are being deployed around the world. These5G networks use emerging technologies to support data and voicecommunications with millions, if not billions, of mobile phones,computers and other devices. 5G technologies are capable of supplyingmuch greater bandwidths than was previously available, so it is likelythat the widespread deployment of 5G networks could radically expand thenumber of services available to customers.

Unlike prior data and telephone networks that relied upon proprietarydesigns, modern 5G networks generally comply with industry standardssuch as the Open Radio Access Network (“Open RAN” or “O-RAN”) standardthat describes interactions between the network and mobile phones andother devices associate with an operator of the network. The O-RAN modelfollows a virtualized model for a 5G wireless architecture in which 5Gbase stations (“gNBs”) are implemented using separate centralized units(CUs), distributed units (DUs) and radio units (RUs). In a modernnetwork, O-RAN CUs and DUs are often implemented using software modulesexecuted by distributed (e.g., “cloud”) computing hardware.

RUs, however, require a cell site with physical transmitters, antennasand the like at an actual geographic location. A major challenge todeploying a 5G network, then, is obtaining the necessary physicalinfrastructure. Even if certain backend computing functions can bevirtualized and deployed fairly readily, it is still necessary toprovide physical radio equipment (e.g., transmitters/receivers,antennas, filters, etc.) in each of the geographic locations wherewireless coverage is desired. The logistical challenges of obtain accessto spectrum, obtaining access to cell towers, supplying data service tothe site and performing maintenance on the physical radio units can bean insurmountable burden, particularly for smaller network serviceproviders.

Although some attempts have been made to share assigned spectrum betweenmultiple networks, these have been met with various challenges. Theso-called “neutral host” model, for example, allows one network providerto lease bandwidth on its own network to other parties. The neutral hostgenerally recognizes the lessee's “roaming” traffic on its own network,and then forwards such traffic to the lessee, generally for a fee. Inthis model, however, the “neutral host” maintains full access andcontrol of its own network, so the other providers that are leasingspace on the network must relinquish a substantial amount offlexibility, security, and control over their data traffic. And even tothe limited extent that some wireless providers may lease dedicatedportions of their spectrum to other providers, this access still lacksthe flexibility and independence that are generally desired fromoperating an independent network.

A substantial desire therefore exists to build systems, devices andautomated processes that would facilitate convenient sharing of spectrumand radio equipment between multiple network operators. In particular,there is a need to flexibly and efficiently apportion spectrum and radioresources amongst multiple guest network operators while allowing theguest operators to independently deploy a wide range of networkservices.

BRIEF SUMMARY

Various embodiments provide 5G access on demand using a dynamic andflexible access on demand model. This model dynamically assigns radioresources (RUs, antennas, etc.) and electromagnetic spectrum in a mannerthat is uniquely tailored for customers' specific services. Unlikeprevious “neutral host” models, the R/SaaS model allows guest mobilenetwork operators (MNOs) to instantiate their own virtualized networkfunctions using dedicated spectrum without the need to obtain and managethe physical resources otherwise needed to support wirelesscommunications. Guest MNOs (e.g., business enterprises, governmententities and/or the like) can implement their own network servicesusing, for example, their own 5G core, IP multimedia system (IMS),virtual CUs, virtual DUs, operations/business support system (OSS/BSS)and/or the like. These service modules communicate with user equipment(UE) via spectrum and radio capabilities that are granted by a networkhost. Guest network operators can maintain control over the virtualizedbackend modules that provide the actual network services without thehost network needing access to the underlying data or limiting theservices that are provided by the guest. Various embodiments thereforeallow guest network operators to obtain spectrum on demand that can beused to manage complete 5G networks fit for their own target services.Such access can be delivered quickly and efficiently, without the guestnetwork operator needing to obtain its own hardware, antennas, spectrum,etc.

This general concept enables a wide range of new network services thatwere previously impractical, if not impossible, to build. Enterprisesand manufacturers, for example, could build and operate their ownspecial-purpose 5G networks to support their own unique services whileserving only the geographic locations and times that are needed. Publicand/or private entities could develop their own 5G networks for publicor private services without relying on legacy MNOs. Customized wirelessnetworks can be created to serve sporting events, festivals or otherpublic events by allocating spectrum only at the locations and timesthat the events occur. Similarly, customized networks could be quicklydeployed to respond to specific emergency situations, natural disasters,police or fire situations and/or the like. Such networks may be deployedonly for those times, locations and bandwidth ranges suited to theservice needs of the particular event. Many other examples ofdynamically-created guest network services could be equivalentlyimplemented using the concepts described herein.

Dynamic allocation provides efficiency and flexibility for guest networkproviders. Guest network operators could modify their own networkservices or deploy new services simply by adapting their own backendinfrastructure, without a need to involve the network host. This enablesflexible and secure services to be quickly deployed for a wide range ofguest network operators. Existing network services can be scaled upwardor downward simply by modifying the cloud computing resources allocatedto the service, thereby making very efficient use of computingresources. Costs can also be saved by allocating only spectrum andcomputing services at the times and places that they are needed.

Dynamic allocation also allows more efficient use of the entire spectrumoperated by the host network. A business or factory, for example, mayneed additional bandwidth in certain locations during the workday thatis not needed after working hours are over. This unneeded bandwidthcould be reassigned to a video streaming service, for example, that seesgreater demands during non-working hours. This dynamic adaptation ofspectrum is particularly efficient when paired with cloud computingresources that can be scaled up or down as needed based upon thethen-current services operating on the network. Dynamic allocation canalso be used to avoid spectrum fragmentation caused by non-contiguousspectrum allocations, if desired. Conversely, dynamic allocation couldbe used to assign bandwidth in those frequencies that are of greatestvalue for the specific services desired by the various MNOs. Lowerfrequencies with higher coverage (but typically lower sub-carrierspacing) can be allocated to voice traffic, for example, while mid- andhigher spectrum bands can be assigned to services that rely upon higherSCS and beamforming capabilities such as drones or robotics. Variousembodiments therefore provide a wide range of network sharing systemsthat are dynamic, flexible and computationally (as well as economically)efficient.

According to various embodiments, a portion of the bandwidth serviced byone or more radio units (RUs) associated with a host provider can bedynamically allocated for use by a “guest” network operator using aprovisioning plane or the like. The guest operator uses the provisioningplane to request available bandwidth on one or more RUs. If therequested bandwidth is available, the provisioning plane thendynamically communicates with the appropriate RUs to create a customizedbandwidth allocation for the guest provider at the desired times,locations and/or radio frequencies. In some embodiments, the guestnetwork operator can maintain its own network services through avirtualized set of CU and/or DU modules (as well as core and IMSmodules), which are all synchronized to the same RUs operated by thehost provider. The guest provider maintains control of its own securenetwork while reliably communicating via dynamically allocated portionsof the host operator's RU spectrum. This allows the guest operator tocreate a highly configurable network using only the bandwidth and RUresources needed for the particular services.

In one example embodiment, an automated process is performed by acloud-based or other data processing system associated with a hostnetwork to dynamically allocate a spectrum that is associated with awireless radio unit (RU) of the host network amongst a plurality ofguest networks each independently delivering one or more networkservices to user equipment (UE) associated with that guest network. Theautomated process suitably comprises: receiving, at a provisioning planeassociated with the data processing system, input data that identifies adesired portion of the spectrum associated with the wireless radio unitfor use by one of the guest networks; in response to the input data, theprovisioning plane allocating the desired portion of the spectrumassociated with the wireless radio unit for exclusive use by the one ofthe guest networks; and broadcasting, via the radio unit, dataidentifying a random access channel (RACH) opportunity to thereby permitthe UEs in communication with the radio unit to responsively synchronizewith the radio unit and to attach to the associated one of the guestnetworks to receive information about the allocated portion of thespectrum from the associated one of the guest networks, and tothereafter communicate with the associated guest network using theportion of the spectrum that is allocated for exclusive use by the guestnetwork.

Another example provides a communications system associated with a hostnetwork. The wireless communication system suitably comprises a wirelessradio unit (RU) configured to broadcast and receive transmissions over aspectrum and a provisioning plane executing on a data processing systemthat is in communication with the radio unit. In various embodiments,the provisioning plane is configured to perform an automated process todynamically allocate a spectrum that is associated with the RU amongst aplurality of guest networks each independently delivering one or morenetwork services to user equipment (UE) associated with that guestnetwork.

Other embodiments may provide other systems, devices and automatedprocesses relating to dynamic allocation of 5G wireless resources, asdescribed in additional detail below.

DRAWING FIGURES

FIG. 1 shows an example of a system for implementing a wireless datanetwork with shared access to spectrum assigned to one or more radiounits.

FIG. 2 shows an example of a provisioning plane that dynamicallyallocates spectrum assigned to one or more radio units to various guestnetworks.

FIG. 3 shows an example allocation of bandwidth in a spectrum assignedto a radio unit.

FIG. 4 illustrates an example of packet scheduling in a shared spectrumenvironment.

FIG. 5 shows an example of an automated process to establishcommunications with user equipment in a shared spectrum environment.

FIG. 6 shows an example of an alternate automated process to establishcommunications with user equipment in a shared spectrum environment.

FIG. 7 illustrates an example process to reassign a bandwidth portion ina shared spectrum environment.

DETAILED DESCRIPTION

The following detailed description is intended to provide severalexamples that will illustrate the broader concepts that are set forthherein, but it is not intended to limit the invention or the applicationand uses of the invention. Furthermore, there is no intention to bebound by any theory presented in the preceding background or thefollowing detailed description.

As noted above, a host operator is able to provide a “radio/spectrum asa service (R/SaaS)” system by dynamically allocating bandwidth on itsown radio units for use by one or more guest network operators. Thisallocation can take place using a provisioning plane that allows guestnetwork operators to select desired times of availability, geographiclocations, amounts of bandwidth/available spectrum bands, and/or otherparameters as desired. The provisioning plane communicates with theparticular radio unit(s) within the 5G network system to apportion theavailable spectrum amongst the various guest operators as desired. Invarious embodiments, each guest operator maintains its own virtualizednetwork functions (e.g., DUs, CUs, 5G Core, IMS, OSS/BSS/IT), therebymaintaining security and control of its own end-to-end network.

The spectrum management features described herein can be very powerfuland flexible. Various embodiments are able to support relatively smallbandwidth allocations (e.g., as small as 5 MHz or even less), as well asnon-contiguous bandwidth allocations if desired. Conversely, spectrumfragmentation can be reduced (if not eliminated) through the dynamicallocation features described herein, since non-contiguous allocationscan simply be restructured. Various embodiments additionally supportmultiple spectrum bands, carrier aggregation, dual connectivity andother features as appropriate.

With reference now to FIG. 1 , in an example system 100 a host operatormaintains ownership of one or more radio units (RUs) 115 associated witha wireless network cell. Each RU 115 suitably communicates with userequipment (UE) 141, 142, 143 operating within a geographic area usingone or more antennas/towers 114 capable of transmitting and receivingmessages within an assigned spectrum 116 of electromagnetic bandwidth.In various embodiments, guest networks 107, 108, 109 interact with aprovisioning plane 105 to obtain desired spectrum (e.g., portions 117,118, 119 respectively) across one or more of the RUs 115 operated by thehost 101. Provisioning plane 105 allows guest network operators 107,108, 109 to obtain or change their assigned bandwidths on different RUs115 on an on-demand and dynamic basis. Other embodiments may processbandwidth allocation according to a predetermined schedule, or in anyother temporal manner as desired.

The Open RAN standard breaks communications into three main domains: theradio unit (RU) that handles radio frequency (RF) and lower physicallayer functions of the radio protocol stack, including beamforming; thedistributed unit (DU) that handles higher physical access layer, mediaaccess (MAC) layer and radio link control (RLC) functions; and thecentralized unit (CU) that performs higher level functions, includingquality of service (QoS) routing and the like. The CU also supportspacket data convergence protocol (PDCP), service data adaptationprotocol (SDAP) and radio resource controller (RRC) functions. The RU,DU and CU functions are described in more detail in the Open RANstandards, as updated from time to time, and may be modified as desiredto implement the various functions and features described herein. In theexample of FIG. 1 , host 101 maintains one or more DUs and CUs as partof its own network. The DU suitably communicates with one or more RUs115, as specified in the Open RAN standard.

The various network components shown in FIG. 1 are typically implementedusing software or firmware instructions that are stored in anon-transitory data storage (e.g., a disk drive or solid state memory)for execution by one or more processors. In particular, the variouscomponents shown in FIG. 1 can be implemented using cloud-based hardware161 and an appropriate operating system 162 such as the Amazon WebService platform provided by Amazon Inc., although other embodimentscould use other cloud platforms and/or any type of conventional physicalcomputing hardware 161, as desired.

As illustrated in FIG. 1 , system 100 suitably includes a host network101 and one or more guest networks 102, 103, 104. The host network 101is typically operated by an organization that owns radio equipment andsufficient spectrum (potentially on different bands) to offer 5Gcapacity and coverage. Host network 101 may or may not be a 5G MNO thatprovides 5G service to its own UEs. Host network 101 will include atleast one DU and at least one CU, both of which will typically beimplemented virtually using cloud resources. If host network 101 doesprovide 5G MNO services, then it will also possess appropriate 5GC, IMS,and IT/OSS/BSS services as appropriate.

One or more guest networks 102, 103, 104 operated by guest operators107, 108, 109 (respectively) can manage their own networks usingallocated portions of the bandwidth 117, 118, 119 handled by one or moreof the RUs 115 associated with the host 101. The guest networks 102,103, 104 are allowed to communicate with one or more UEs 141-143 usingallocated bandwidth 117, 118, 119 on the host's RU 115. Guest networks102, 103, 104 may include one or more virtual DUs and CUs, as well asunique core functions and IP multimedia subsystems (IMS), as desired.Generally, one or more guest operators will instantiate its own 5Gvirtualized network functions (e.g., IMS, vCUs, vDUs, and IT/OSS/BSS)using cloud-based resources, as noted above.

Guest operators lease or otherwise obtain any needed 5G access for itsplanned services, capacity and coverage based on an arrangement with thehost provider. A guest provider then operates and manages its own 5Gnetwork 107, 108, 109 independently of the host 101 and the otherguests. As noted herein, an orchestrator aligns all the playersincluding the host and all the guests. A network operator can optimizeits own network for unique target services by intelligently selectingits spectrum, RUs, vDU/MAC scheduler, vCU and 5G Core and IMS NFs, asdescribed more fully herein.

The provisioning plane 105 cooperates with the RUs 115 in various cellsto supply the requested bandwidth at the requested times. Generallyspeaking, guest operators 107, 108, 109 communicate with the hostnetwork 101 via provisioning plane 105, which executes on real orvirtual hardware 161 within system 100. The provisioning plane 105typically retains public land mobile network (PLMN) informationidentifying primary (PCell) and secondary (SCell) cells associated withthe various RUs 115, as well as the times and bandwidths assigned oneach cell. In various embodiments, the provisioning plane 105 identifiesthe allocated spectrum on each RU 115 according to physical resourceblocks (PRBs) that can be stored for later processing and retrieval.Portion 118, for example, is described by one or more PRBs of spectrum116, and portion 119 is described by a different set of PRBs. As notedabove, bandwidth to any guest operator may be non-contiguous, ifdesired. Each guest network will typically maintain a copy of its ownPLMN, bandwidth and timing information, but there is generally no needfor guests to share information about each other.

Each RU 115 is typically associated with a different wireless cell thatprovides wireless data communications to user devices 141-143. RUs 115may be implemented with radios, filters, amplifiers and othertelecommunications hardware to transmit digital data streams via one ormore antennas 114. Generally, RU hardware includes one or moreprocessors, non-transitory data storage (e.g., a hard drive or solidstate memory) and appropriate interfaces to perform the variousfunctions described herein. RUs are physically located on-site with thetransmitter/antenna 114, as appropriate. Conventional 5G networks maymake use of any number of wireless cells spread across any geographicarea, each with its own on-site RU 115.

RUs 115 support wireless communications with any number of user devices141-143. User devices 141-143 are often mobile phones or other portabledevices that can move between different cells associated with thedifferent RUs 115, although 5G networks are also widely expected tosupport home and office computing, industrial computing, robotics,Internet-of-Things (IoT) and many other devices. While the exampleillustrated in FIG. 1 shows one RU 115 for convenience, a practicalimplementation will typically have any number of RUs 115 that can eachbe individually configured to provide highly configurable geographiccoverage for a guest network, if desired.

Referring now to FIG. 2 , an example of a provisioning plane 105 isimplemented using cloud computing resources to facilitate sharing ofspectrum associated with one or more RUs 115. Configuration plane 115 isimplemented within an application program interface (API), web interfaceor the like that allows guest operators to supply appropriate parametersto obtain desired network access. In the example of FIG. 2 , a graphicalinterface 202 suitably includes input features for the guest operator tosupply desired times, locations and/or bandwidth requests. Bandwidthrequests may be specified in terms of frequencies, if desired, or byservices (e.g., voice, robotics, drones, data, etc.) as appropriate. Asnoted above, some guest operators may wish to obtain specific low,medium and/or high frequencies based upon the specific services thatthey intend to provide. Network operators can also specify dates and/ortimes that the spectrum is requested, as well as particular locations.Various embodiments could specify locations according to RU identifiers,if available, although other embodiments could allow allocation ofresources according to ZIP code, city/county, state or other geographicparameters. Cost information associated with the requested spectrum mayalso be presented, if desired. The example interface 202 is intended topresent the types of information that could be presented; a practicalimplementation may appear very different from the illustration of FIG. 2, and/or may present the information shown in any number of differentscreens.

Provisioning plane 105 suitably supports communications between the hostnetwork 101 and guest networks 102, 103, 104 to request for anyadjustments in allocated 5G access. In this communication, the guest102, 103, 104 typically provides a set of its network identifiers (e.g.,identifiers for a home public land mobile network (HPLMN) and anyroaming public land mobile networks (PLMNs)) to the host 101. Thispermits the host 101 to broadcast all of the PLMN IDs of all of theguests 102, 103, 104 in the system information block (SIB) as discussedbelow. The host 101 also informs each guest 102, 103, 104 of its leasedspectrum resources, i.e., the physical resource block (PRB) setallocated to the guest in each leased band.

FIG. 2 also illustrates a billing system 204 that may be implementedusing cloud resources or the like. In various embodiments, guest networkoperators are billed for their allocated spectrum according to a leaseagreement or the like. By allowing guest operators to request only thespectrum that is needed in desired locations and at desired times,considerable cost savings can be realized compared to leasing entirefrequency bands at all possible times and locations as in most currentleasing arrangements.

Additionally, allocated spectrum can be scaled up or down and/oradditional times and locations can be allocated as desired, often withlittle or no lag time. In various embodiments, spectrum 115 can beallocated or de-allocated in real time, or very near real time(accounting for some delay that is inherent in data processing and datacommunications). Billing system 204 suitably charges each guest networkonly for the services actually allocated and used, thereby allowing forsubstantial cost efficiencies without sacrificing the ability to quicklyramp up additional services.

In operation, then, the provisioning plane 105 suitably configuresshared spectrum 116 on one or more particular RUs 115. Generally, aguest network operator will establish a connection with provisioningplane 105 via an API or web interface. The operator will typically beauthenticated with suitable digital credentials (e.g., userid/password,digital signatures, biometrics and/or the like). When authenticated, theguest operator is able to supply appropriate parameters (e.g., time,location, frequency bands) for requested network access. Theprovisioning plane 105 appropriately determines if the requested accessis available, and if so, the appropriate RU(s) 115 are notified throughthe host network 101. Provisioning plane 105 also interacts with abilling system 204 as appropriate.

In various embodiments, each guest network communicates the allocatedportions 117, 118, 119 of spectrum 116 to its associated UEs 141, 142,143 through 3GPP bandwidth portions (BWPs) or the like. BWPs allow theguest network to confine the bandwidth used by a particular UE 141, 142,143 to a particular frequency range. In the 3GPP standard, each UE 141,142, 143 can be assigned up to four BWPs for upload or download, andBWPs can overlap if desired.

In the example illustrated in FIG. 3 , each portion 117, 118, 119allocated to guest networks 102, 103, 104 (respectively) is described bya range of BWPs that are assigned by the guest networks 102, 103, 104.Guests manages its own portion 117, for example, with a “main BWP” 302that describes the entire allocated frequency band 117, with morelimited bands 303, 304, 305 for specific upload or download functions.Each of these BWPs 302-305 are communicated to UEs 141 associated withthat guest network, noting that each UE 141 may receive its own BWP set.Each UE 141 may have a unique set of assigned BWPs 302-305 within theassigned portion 117 of spectrum 116, as appropriate. Other embodimentsmay assign the same or similar BWPs 302-305 to multiple UEs 141, ifdesired. The guest network may assign BWPs 303, 304, 305 (as well as anyother BWPs within the allocated band 117) as desired to any number ofUEs 141 for appropriate uplink and downlink communications as desired.

BWPs may be communicated to the UEs 141 associated with each guestnetwork in any manner. In various embodiments, the provisioning plane105 communicates the assigned frequency bands 117, 118, 119 to guestnetworks 102, 103, 104. The guest networks, in turn, each assign BWPs toparticular UEs 141 and communicate the assigned BWPs to each UE 141 asdesired. In various embodiments, a CU associated with the guest(discussed below) communicates BWP information using RRC signaling orthe like. Other embodiments could use other protocols for deliveringfrequency band assignments to associated UEs 141, as desired. BWPswitching could be managed using downlink control information (DCI) froma guest DU, for example. Other embodiments using other protocols andsignaling techniques could be equivalently used.

FIG. 3 also shows an initial BWP 308 within spectrum allocated to hostnetwork 101 (although other implementations may assign the initial BWP308 in any other portion of spectrum 116). In various embodiments, thisinitial BWP 308 is assigned to facilitate initial attachment with the UE141, 142, 143 as described more fully below. This shared initial BWP 308supports timing synchronization between the various networks 101, 102,103, 104 so that guard bands may not be necessary. That is, devices 141,142, 143 associated with host network 101 or any guest network 102, 103,104 will synchronize to the RU 115 in both time and frequency, and onboth uplink and downlink traffic, as described more fully below. Thiswill cause the waveforms of the various signals sent and received by UEs141, 142, 143 to be orthogonal, thereby eliminating interference witheach other. Time synchronization between RU 115 and the various DUs andCUs operating in networks 101, 102, 103, 104 may also be needed in someembodiments.

Although UL and DL traffic is synchronized to the host 101, each guestnetwork autonomously manages and schedules its own physical resourceblocks (PRB) over its allocated spectrum. The host RU 115 will generallymonitor spectrum transmissions to ensure compliance with the assignedschedule. But each guest operator designs its own scheduler (e.g., inits own virtual DU) for processing its own network services.

FIG. 4 illustrates an example of a system 400 in which spectrum 116 isassigned into different portions 120, 117, 118, 119 as described above.The host 101 maintains its own scheduler 402 for processing items inhost queue 403. Similarly, guest operators 102, 103 and 104 maintaintheir own schedulers 405, 410 and 415 to process items in their ownqueues 406-407, 411-412 and 416-417, respectively.

Typically, schedulers 402, 405, 410 and 415 are implemented within cloudcomputing resources associated with a virtual DU. In the example of FIG.4 , each guest network would maintain its own separate DU to schedulecommunications within its own assigned bandwidth parts. In otherembodiments, host network 101 could also provide a shared DU to some orall of the different guests sharing the spectrum 116. In a shared DUimplementation, each guest could maintain its own virtual CU, 5G coreand IMS functions using cloud computing resources. Still otherembodiments could allow host 101 to provide both shared DU and CUfeatures that support the guest's 5G core and IMS functions, as desired.The various shared functions could be mixed and matched as desired, withsome guests using shared resources as may be available and other guestsusing their own resources, as appropriate. That is, some guest operatorsmay make use of shared DU and/or CU resources from host network 101while other guest operators provide their own virtual DU and/or CUfunctions, as desired.

FIGS. 5 and 6 show several examples of automated processes 500, 600 tohandle communication using the shared spectrum 116 while maintainingseparate networks for host 101 and guests 107, 108. In the example ofFIG. 5 , a process 500 allows a guest network 102 to maintain control ofrandom uplink channels by providing its own virtual DU(s) 506 asdesired. In the example of FIG. 6 , a similar process 600 allows forhost control of the random uplink channel (PRACH) using a shared DU 502,as appropriate. Both implementations use shared downlink synchronizationto transmit the appropriate scheduling information to devices operatingin communication with RU 115. Commonly labeled elements of FIGS. 5 and 6therefore refer to very similar, if not identical features andfunctions. Additionally, although this example uses a single guestoperator 107 for clarity, practical embodiments will simultaneouslyprovide equivalent functions and features for any number of additionalguest operators 108, 109.

With reference now to FIG. 5 , a guest network operator uses theconfiguration plane 105 described above to request bandwidth allocationsat desired times and places. Various embodiments may also allow theguest to request contiguous bandwidth (potentially for an additionalfee), or to select other parameters as desired. In various embodiments,configuration plane 105 interacts with a billing system 204 or the likeso that the host provider can be paid for leased portions of thenetwork. As noted above, provisioning plane 105 may provide a suitableuser interface 202 that allows an operator to enter desired parameters.The allocated bandwidth portions on each RU 115 are communicated withinhost network 101 to the host DU 502 that is associated with the RU 115.

Spectrum 116 associated with each RU 115 can be allocated in any manner(function 510). In various embodiments, the provisioning plane 105suitably allocates bandwidth for each leased portion 117, 118, 119 andcommunicates this information to the relevant RU 115, and to each guestnetwork 107, i08, 109. RU 115 enforces the assigned schedule, but eachguest network 107, 108, 109 is responsible for communicating itsassigned bandwidth to its own UEs 141, 142. This isolates informationbetween the different guest networks 107, 108, 109 while still allowingfor synchronization of all the UEs 141, 142 operating within range of RU115.

Host network 101 maintains responsibility for uplink (UL) and downlink(DL) system synchronization. To that end, adjoining frequency bands 117,118,119 can be time and frequency synchronized to the host network 101,thereby reducing (or even eliminating) the need for bandwidth separationbetween PRBs. To maintain synchronization, the DU 502 associated withthe host network 101 formats synchronization signal blocks (SSB)(function 204) that are broadcast on the downlink of the RU 115 to alluser devices 141, 142 without regard to the network 101, 102, 103 usedby that device. Each of the UEs 141, 142 operating on a cell will sharethe same downlink synchronization data. The SSB 514 typically includesconventional 5G information such as primary synchronization schedule(PSS), secondary synchronization schedule (SSS), physical broadcastchannel (PBCH) data and/or the like. The SSB 514 is broadcast by RU 115so that all devices 141, 142 are able to receive and process the sametime and frequency synchronization information (functions 516, 517).

Each user device 141, 142 synchronizes to the downlink using thereceived SSB broadcast 514 (functions 516, 517). As noted above, the SSB514 is typically broadcast periodically at predictable time intervals,and contains sufficient PSS, SSS and other data to allow each UE 141,142 to time and frequency synchronize to the host downlink. SSB periodsmay be configurable, but are often chosen to be between about 5 andabout 160 msec, with a default value of about 20 msec, although otherembodiments could use different intervals as desired. The SSB 514 willtypically include master block information (MIB) within the PBCH, whichprovides enough information for each UE 141, 142 to obtain the systeminformation block (SIB), often in SIB-1 format.

Host DU 502 therefore formats system information 518 that can besimultaneously broadcast to each of the devices 141, 142 in accordancewith the timing information contained in the SSB 514. Conventional 5Gmajor information blocks (MIBs), system information blocks (SIBs) andon-demand system information (OSI) can be scheduled and broadcast by DU115. Generally, the MIB data is transmitted in the physical broadcastchannel described by the SSB 514 discussed above. Generally, SIBs 518are generated periodically, and can be scheduled through the MIBcontained within SSB 514. In some equivalent implementations, the SIBs518 are provided in response to an on-demand other signal information(OSI) message sent by the UE 141, 142, as appropriate.

In various embodiments, the SIB 518 broadcast includes the PLMNsassociated with each guest network 102, 103 operating within the cell,thereby allowing UEs 141, 142 to recognize their associated PLMN and toinitiate contact with RU 115 as described herein. Other systeminformation (OSI) can be scheduled and broadcast within the allocatedportion assigned to a guest operator, if desired. Alternately, OSIinformation may be scheduled by the host 101 for subsequent broadcastthrough cooperation with the guest operators as desired.

Each user device 141, 142 uses information contained within the SIB 518to make initial contact with that device's PLMN (functions 519, 521).After attachment with the UE 141, 142, each guest network 102, 103 willschedule its own uplink and downlink traffic on its assigned PRBs, asdescribed herein. The host RU 115 suitably monitors the schedule ofassigned PRBs, however, to ensure that guest devices operate only overthe allocated PRBs (function 212) and to prevent spillover or othermis-use of unallocated spectrum. RUs 115 may enforce the schedule bydiscarding or ignoring non-compliant traffic, by responding tonon-compliant traffic with an error message, and/or by taking otheractions as desired.

To initially attach to the appropriate network, user devices 141, 142use a synchronized physical random access uplink channel (PRACH) asappropriate. Initial uplink communications from user devices 141, 142can take place in any number of different ways. In various embodiments,the 5G random upload channel (PRACH) can be managed in any number ofdifferent ways to provide efficient throughput of uploaded data. In theexample of FIG. 5 , different PRACHs are terminated using different DUs502, 506. In the example of FIG. 6 , a shared PRACH is terminated usingthe host DU 502. Additional PRACHs may be terminated using the host DU502, if desired.

As noted above, each device 111, 112 receives synchronization signals(SSB) 514, SIB 518 and physical random access channel (PRACH)opportunity data that are configured, scheduled and broadcast by thehost DU 502. All of the devices 141, 142 therefore synchronize to thehost network 101 on the download link, and to obtain uplink information.To attach to the appropriate network, the device 141, 142 suitablytransmits a message on the appropriate uplink identified in the SIB 518.The host DU 502 typically receives the preamble sequence from the UE,measures any timing error, and sends a timing advance (TA) command backto the UE 141, 142. This TA command will allow the device to synchronizeon subsequent UL communications, as needed.

In some implementations (e.g., 3GPP Releases 15 and 16), DU 502 willforward any attachment messages to the host CU 504 so that the UE 141,142 can be matched to its appropriate network. Typically, the host CU504 will compare any PLMN identifiers in the uplink message against atable of recognized PLMNs. If the PLMN of the device 141, 142 isrecognized, then the message is forwarded 505 to the relevant guest CU508 for further processing, if the guest provides its own CU 508 (as inFIG. 5 ). If the guest does not provide its own CU 508, then the host CU508 may forward the message to the appropriate guest network resourcesfor further processing. If the received uplink messages is a radioresource control (RRC) message, for example, that message can beforwarded to a central unit control plane associated with theappropriate network 101, 102, 103 for termination. Similarly, non-accessstratum (NAS) or similar messages can be transmitted for termination atthe appropriate core network 101, 102, 103. The guest network then takesover to complete the attachment process, including authentication,service authorization, slice selection, packet data unit (PDU) sessioncreation, etc.

After the device 141, 142 is recognized, subsequent communications maybe processed more efficiently. In the example of FIG. 5 , the guestnetwork maintains its own DU 506. The RU 115 may be notified (e.g., fromhost DU 502) that subsequent communications from the recognized deviceshould be forwarded directly to guest DU 506, as shown by message 528.Guest DU 506 will then forward traffic 530 through its own CU 508, asdesired. In other embodiments, the guest network may use host DU 502resources instead of its own. After initial attachment, host CU 504 willtypically notify the host DU 502 that subsequent communications 602associated with the now-recognized device 141, 142 should be forwardedto the guest CU 508, as shown in FIG. 6 . Many other embodiments couldprocess attachment and subsequent communications in any other manner, asdesired.

As 3GPP and other standards become more mature, it may be possible tomake use of future features in the initial attach process. 3GPP Release17, for example, may include radio access network (RAN) slicing featuresthat could be used to recognize an attaching device 141, 142 based uponits PLMN-ID and to quickly direct traffic from that device towards anappropriate guest network 107, 108, 109 as desired. A “slice-based” RACHconfiguration feature in 3GPP Release 17, for example, could allowmapping of slice-IDs to PRACH occasions. By mapping slice identifiers tospecific guest networks 107, 108, 109, each UE 141, 142 would be able tomessage its own network indirectly (through the RU 115) but immediatelyusing the appropriate RACH occasion for its assigned network. A sliceidentifier could further include a slice service type (SST) and a slicedifferentiator (SD). If the SD value were mapped to disjoint ranges andeach range was assigned to a different guest network, then the systemcould use this information to quickly differentiate devices belonging todifferent networks based upon the SD of the received slice identifier.This arrangement would also allow each guest network to support multipleslices of the same service type. Still other embodiments could usefuture standardization efforts in 3GPP or the like to support PLMN basedPRACH occasions, if and when such features become available.

After attachment, each guest network 107, 108, 109 communicates with itsassociated UEs 141, 142 using that network's allocated portions ofspectrum 116. In various embodiments, a CU 508 associated with theappropriate network will assign bandwidth parts (BWPs) to eachassociated UE 141, 142 (shown with message 535 in FIGS. 5 and 6 ). BWPsfor each UE 141, 142 can be communicated to that UE 141, 142 via RRCsignaling or the like. As noted above (e.g., in the discussion of FIG. 3), each UE 141, 142 can be assigned up to four different BWPs for eachof uplink and downlink, and BWPs can overlap if desired. The appropriateCU 508 will communicate the assigned BWPs to each UE 141, 142, whichwill then use the assigned frequency bands for subsequent communication.Other embodiments could use other protocols for delivering frequencyband assignments to associated UEs 141, 142, as desired. BWP switchingcould be managed using downlink control information (DCI) from the guestDU 506, for example, in an equivalent embodiment.

One benefit of dynamic spectrum allocation is that networks can bereadily re-configured without disrupting operations. Modifications canhappen as one or more guests scale their bandwidth allocations upward ordownward, or for any other reason. As mentioned previously, spectrum canbe readily reconfigured to avoid spectrum fragments, if desired.Although fragments may be desirable in some circumstances (e.g., a guestrequests bandwidth for both low-frequency and high-frequency services),generally the network will operate more efficiently if bandwidthfragments are reduced.

FIG. 7 shows one example of a spectrum allocation 710 between two guestnetworks that can be de-fragmented into a new allocation 720. In theinitial allocation 710, one guest network is initially associated withtwo separate fragments 702 and 705, and another guest network isinitially associated with a contiguous fragment 708. If it is desired tode-fragment the spectrum allocation, then each network will generallytemporarily re-assign UEs using BWPs in the transitioning fragments touse other portions of the spectrum.

In the example of FIG. 7 , it is necessary to change the frequencyranges of both guests operating in the spectrum since the frequencies indesired allocation 720 of both guest networks overlap with thefrequencies currently assigned in allocation 710. To support this, a“dummy” frequency range 715 can be used to temporarily transitioncertain UEs associated with one of the guests until contiguous bandwidthcan be freed up. Although FIG. 7 shows the dummy portion 715 in thelower frequency range of the spectrum, alternate embodiments couldequivalently use higher frequencies, or any other frequency bands thatmay be available to support the types of traffic being conducted by UEs141, 142 while using the dummy portion 715.

Each guest network initially re-assigns those UEs operating within thetransitioning frequency bands to another range. One way to accomplishthe example of FIG. 7 would be for the second guest network to initiallytransition any use of band 703 to the dummy band 715. This would occurby the guest network sending update messages to the relevant UEs 141,142 and providing some time (e.g., a few seconds) for the devices totransition into the new frequency band 715. After all of the UEs 141,142 previously operating within band 703 have been moved to band 715,then band 703 may be dis-associated with the second guest network andre-assigned to the first guest network. The first guest network wouldthen transition any devices using band 705 into the now-available band703. The first guest network would therefor operate on bands 702 and703, thereby forming a contiguous band 712. Specific operations withinband 712 could then be managed by the first guest network, as desired.

After the first guest network has ceased operations within band 705, theband can be re-assigned for use by the second guest network. Typically,the second guest network will move devices operating in the dummy band715 into the new range 705, but reassignment could allow devicesassociated with the second guest network to operate anywhere within thenew contiguous frequency range 713 that is now associated with thesecond guest network.

The various re-assignments described herein may be managed by theconfiguration plane 105 which appropriately communicates with the hostand guest networks 101, 102, 103, 104 to process the re-assignmentsusing new BWP assignments or the like. To that end, configuration plane105 is able to re-configure the bandwidth allocations 116, 117, 118, 119associated with the various host and guest networks as desired. Suchre-configuration may take place in real time in response to guestnetwork operator requests, host operator requests, changing network orenvironmental conditions, and/or any other factors as desired.

The general concept of dynamic bandwidth allocation is especiallypowerful when combined with the scalability of backend services providedby cloud computing. Guest network operators can rapidly and dynamicallyobtain and release cloud computing resources from the cloud computinghost on an as-needed basis, thereby preventing purchase of excessivecapabilities while retaining the ability to handle expected orunexpected peak loads. Guest network operators may instantiateadditional virtual modules, for example, to address additional demand asneeded. Similarly, various embodiments may allow fast acquisition ofadditional computing resources (e.g., more processing capability or datastorage) for existing virtual modules, if desired. Because the guestnetwork operator is no longer constrained by the need to obtain spectrumand physical infrastructure, customized 5G networks can very rapidly bedeployed on any scale, having any desired capability, and for anydesired time periods.

As noted above, computing components shown in the figures may beimplemented using cloud-type hardware that abstracts the processor,non-transitory data storage and conventional input/output interfacesthat are found in traditional computing hardware. RUs 115 will generallyinclude radio unit (RU) specific hardware, including processors,non-transitory data storage and conventional input/output interfacesthat are typically used within the wireless industry. Generallyspeaking, the various components shown in FIGS. 5-6 will format messagesand perform the various functions shown in the diagram under the controlof computer-executable instructions (e.g., software or firmware code)that are stored in the non-transitory storage for execution by one ormore processors. Equivalent embodiments could use any types of computinghardware, including any combination of conventional and cloud-basedhardware.

What is claimed is:
 1. An automated process performed by a dataprocessing system associated with a host network to dynamically allocatea spectrum that is associated with a wireless radio unit (RU) of thehost network amongst a plurality of guest networks each independentlydelivering one or more network services to user equipment (UE)associated with that guest network, the automated process comprising:receiving, at a provisioning plane associated with the data processingsystem, input data that identifies a desired portion of the spectrumassociated with the wireless radio unit for use by one of the guestnetworks; in response to the input data, the provisioning planeallocating the desired portion of the spectrum associated with thewireless radio unit for exclusive use by the one of the guest networks;and broadcasting, via the radio unit, data identifying a random accesschannel (RACH) opportunity to thereby permit the UEs in communicationwith the radio unit to responsively synchronize with the radio unit andto attach, using the RACH opportunity, to the associated one of theguest networks and thereby receive information about the allocatedportion of the spectrum from the associated one of the guest networks,and to thereafter communicate with the associated guest network usingthe portion of the spectrum that is allocated for exclusive use by theguest network.
 2. The automated process of claim 1 wherein theallocating occurs substantially in real time in response to receivingthe input data.
 3. The automated process of claim 1 wherein the inputdata describes limited times that the portion of the spectrum isdesired, and wherein provisioning plane assigns the desired portion ofthe assigned spectrum for use by the guest network during the limitedtimes, and wherein the provisioning plane releases the desired portionfor other use outside of the limited times.
 4. The automated process ofclaim 1 further comprising re-configuring, by the host network system,the portion of the spectrum allocated for exclusive use by the guestnetwork without disrupting operation of the guest network.
 5. Theautomated process of claim 4 wherein the re-configuring comprises:re-directing UEs operating in an initially-allocated portion of thespectrum to a temporary frequency band; de-allocating at least a portionof the initially-assigned spectrum associated with the wireless radiounit for exclusive use by the one of the guest networks; allocating anew portion of the spectrum for exclusive use by the one of the guestnetworks; and re-directing UEs operating in the temporary frequency bandto the new portion of the spectrum.
 6. The automated process of claim 4wherein the re-configuring comprises de-fragmenting portions of thespectrum that are assigned to different guest networks into newcontiguous portions.
 7. The automated process of claim 1 furthercomprising formulating, by a distributed unit (DU) of the host network,a synchronization signal block (SSB) message, and wherein thebroadcasting comprises transmitting the SSB to each of the radio units.8. The automated process of claim 7 wherein the SSB comprisessynchronization information that permits the UEs to receive a systeminformation block (SIB) subsequently broadcast by the RU.
 9. Theautomated process of claim 7 wherein each of the UEs is time andfrequency synchronized to the host network using information in the SSB.10. The automated process of claim 9 wherein the allocating comprisesassigning the portions of the spectrum for exclusive use by each of theguest networks without assigning guard bands between allocated portions.11. The automated process of claim 1 wherein a distributed unit (DU) incommunication with the radio unit recognizes the UE associated with oneof the guest networks based upon a primary land mobile network (PLMN)identifier in an uplink message received via the RACH opportunity. 12.The automated process of claim ii wherein the DU forwards the uplinkmessage to a centralized unit (CU) that is associated with the guestnetwork.
 13. The automated process of claim 12 wherein the CU associatedwith the guest network assigns bandwidth parts (BWPs) within theassigned portion of the spectrum to the UE for subsequentcommunications.
 14. The automated process of claim 13 wherein the BWPsare communicated to the UE via a radio resource controller (RRC) messagefrom the CU associated with the guest network.
 15. The automated processof claim ii wherein the DU forwards assigned bandwidth parts (BWPs)within the assigned portion of the spectrum to the UE via downlinkcontrol information (DCI), and wherein the UE uses the assigned BWPs forsubsequent communications via the radio unit.
 16. A wirelesscommunication system associated with a host network, the wirelesscommunication system comprising: a wireless radio unit (RU) configuredto broadcast and receive transmissions over a spectrum; and aprovisioning plane executing on a data processing system that is incommunication with the radio unit, wherein the provisioning plane isconfigured to perform an automated process to dynamically allocate aspectrum that is associated with the RU amongst a plurality of guestnetworks each independently delivering one or more network services touser equipment (UE) associated with that guest network, the automatedprocess comprising: receiving, at a provisioning plane associated withthe data processing system, input data that identifies a desired portionof the spectrum associated with the wireless radio unit for use by oneof the guest networks; and in response to the input data, theprovisioning plane allocating the desired portion of the spectrumassociated with the wireless radio unit for exclusive use by the one ofthe guest networks; wherein the wireless communication system is furtherconfigured to broadcast, via the radio unit, data identifying a randomaccess channel (RACH) opportunity to thereby permit the UEs incommunication with the radio unit to responsively synchronize with theradio unit and to attach, using the RACH opportunity, to the associatedone of the guest networks and thereby receive information about theallocated portion from the associated one of the guest networks, and tothereafter communicate with the associated guest network using theportion of the spectrum that is allocated for exclusive use by the guestnetwork.
 17. The wireless communication system of claim 16 furthercomprising a distributed unit (DU) in communication with the radio unit,wherein the DU is configured to recognize the UE associated with one ofthe guest networks based upon a primary land mobile network (PLMN)identifier in an uplink message received via the RACH opportunity and toforward the uplink message to a centralized unit (CU) that is associatedwith the guest network.
 18. The wireless communication system of claim17 wherein the CU associated with the guest network assigns bandwidthparts (BWPs) within the assigned portion of the spectrum to the UE forsubsequent communications, and wherein the BWPs are communicated to theUE via a radio resource control (RRC) message from the CU associatedwith the guest network.
 19. The wireless communication system of claim17 wherein the DU forwards assigned bandwidth parts (BWPs) within theassigned portion of the spectrum to the UE via downlink controlinformation (DCI), and wherein the UE uses the assigned BWPs forsubsequent communications via the RU.
 20. The wireless communicationsystem of claim 16 wherein the allocating comprises configuring, by thedata processing system, physical resource blocks (PRBs) of the spectrumthat correspond to the allocated portion of the assigned spectrum, andwherein each guest network assigns bandwidth parts (BWPs) within itsassigned PRBs to UEs associated with that guest network.